-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: adds info about restore and backup/repair tasks interference #4124
Conversation
I'm not sure which SM version will contain changes made in #4122, so I've put 3.5 version in the docs temporarily. |
3.5 is a good candidate - we shouldn't put it into 3.4.1 as this is a feature. |
For docs oriented PRs, It's always good to request a review from someone from the product team (e.g. @annastuchlik). They don't always have the time to go through it, so not all docs related PRs need their approval. |
533c285
to
74a3414
Compare
@VAveryanov8 is this PR ready for re-review? |
@Michal-Leszczynski btw: do we use labels to set the target version for PRs? |
In theory we should. I was talking about it during our meeting, but then I figured that if we stick to SEMVER, then patch releases would be really rare for SM, so hand picking commits for them does not seem that bad. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@VAveryanov8 the other PR documenting previous behavior has been merged. |
74a3414
to
53166ea
Compare
53166ea
to
cafd48d
Compare
This extends restore procedure docs with how to avoid conflicts between restore and backup/repair tasks in a cluster.
Fixes: #3742
Please make sure that: